| Package | hl7.ehrs.ehrsfmr21 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-CP.4.2.3.html |
| Url | http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CP.4.2.3 |
| Version | 2.1.0 |
| Status | active |
| Date | 2024-11-26T16:30:50+00:00 |
| Name | CP_4_2_3_Medication_Order_Efficiencies |
| Title | CP.4.2.3 Medication Order Efficiencies (Function) |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | Provide the tooling necessary to increase the efficiency of medication ordering. |
| Purpose | Make medication ordering workflows more efficient by allowing medications to be sorted and reviewed by key attributes (e.g., generic or trade names). Also support editing medication orders across multiple instances of an order and capturing medication orders in order sets. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Provide the tooling necessary to increase the efficiency of medication ordering.
Make medication ordering workflows more efficient by allowing medications to be sorted and reviewed by key attributes (e.g., generic or trade names). Also support editing medication orders across multiple instances of an order and capturing medication orders in order sets.
| CP.4.2.3#01 | SHOULD |
The system SHOULD provide the ability to present a list of medications based on an attribute of the medication (e.g., partial medication name, therapeutic class, or formulary). |
| CP.4.2.3#02 | SHOULD |
The system SHOULD provide the ability to present a list of medications based on an attribute of the patient (e.g., proposed treatment, patient condition, order set, age, gender). |
| CP.4.2.3#03 | SHOULD |
The system SHOULD provide the ability for the clinician to edit medication administration instructions and link it to the corresponding instances of that medication order. |
| CP.4.2.3#04 | SHOULD |
The system SHOULD provide the ability to extract, update and store a prescription reorder by allowing a prior prescription to be reordered without re-entering previous data (e.g., administration schedule, quantity, SIG). |
| CP.4.2.3#05 | SHOULD |
The system SHOULD provide the ability to extract, update and store a prescription reorder from a prior prescription using the same dosage but allowing for editing of details adequate for correct filling and administration of medication (e.g., dose, frequency, body weight). |
| CP.4.2.3#06 | MAY |
The system MAY provide the ability to extract, update and store a prescription renewal from a prior prescription using a different dosage but allowing for editing of details adequate for correct filling and administration of medication (e.g., dose, frequency, body weight). |
| CP.4.2.3#07 | SHALL |
The system SHALL conform to function [[CP.4.1]] (Use Order Sets). |
| CP.4.2.3#08 | SHALL |
The system SHALL provide the ability to extract and render medications by generic, and/or brand name. |
FHIR{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-CP.4.2.3",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Provide the tooling necessary to increase the efficiency of medication ordering.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>Make medication ordering workflows more efficient by allowing medications to be sorted and reviewed by key attributes (e.g., generic or trade names). Also support editing medication orders across multiple instances of an order and capturing medication orders in order sets.</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.4.2.3#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to present a list of medications based on an attribute of the medication (e.g., partial medication name, therapeutic class, or formulary).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.4.2.3#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to present a list of medications based on an attribute of the patient (e.g., proposed treatment, patient condition, order set, age, gender).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.4.2.3#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability for the clinician to edit medication administration instructions and link it to the corresponding instances of that medication order.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.4.2.3#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to extract, update and store a prescription reorder by allowing a prior prescription to be reordered without re-entering previous data (e.g., administration schedule, quantity, SIG).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.4.2.3#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to extract, update and store a prescription reorder from a prior prescription using the same dosage but allowing for editing of details adequate for correct filling and administration of medication (e.g., dose, frequency, body weight).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.4.2.3#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to extract, update and store a prescription renewal from a prior prescription using a different dosage but allowing for editing of details adequate for correct filling and administration of medication (e.g., dose, frequency, body weight).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.4.2.3#07</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL conform to function [[CP.4.1]] (Use Order Sets).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CP.4.2.3#08</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to extract and render medications by generic, and/or brand name.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CP.4.2.3",
"version" : "2.1.0",
"name" : "CP_4_2_3_Medication_Order_Efficiencies",
"title" : "CP.4.2.3 Medication Order Efficiencies (Function)",
"status" : "active",
"date" : "2024-11-26T16:30:50+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Provide the tooling necessary to increase the efficiency of medication ordering.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"purpose" : "Make medication ordering workflows more efficient by allowing medications to be sorted and reviewed by key attributes (e.g., generic or trade names). Also support editing medication orders across multiple instances of an order and capturing medication orders in order sets.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.4.2.3-01",
"label" : "CP.4.2.3#01",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to present a list of medications based on an attribute of the medication (e.g., partial medication name, therapeutic class, or formulary).",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.7.1#4"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.4.2.3-02",
"label" : "CP.4.2.3#02",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to present a list of medications based on an attribute of the patient (e.g., proposed treatment, patient condition, order set, age, gender)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.4.2.3-03",
"label" : "CP.4.2.3#03",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability for the clinician to edit medication administration instructions and link it to the corresponding instances of that medication order."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.4.2.3-04",
"label" : "CP.4.2.3#04",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to extract, update and store a prescription reorder by allowing a prior prescription to be reordered without re-entering previous data (e.g., administration schedule, quantity, SIG).",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.7.1#14"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.4.2.3-05",
"label" : "CP.4.2.3#05",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to extract, update and store a prescription reorder from a prior prescription using the same dosage but allowing for editing of details adequate for correct filling and administration of medication (e.g., dose, frequency, body weight).",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.7.1#15"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.4.2.3-06",
"label" : "CP.4.2.3#06",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to extract, update and store a prescription renewal from a prior prescription using a different dosage but allowing for editing of details adequate for correct filling and administration of medication (e.g., dose, frequency, body weight)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.4.2.3-07",
"label" : "CP.4.2.3#07",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL conform to function [[CP.4.1]] (Use Order Sets).",
"derivedFrom" : "EHR-S_FM_R1.1 DC.1.7.1#10"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CP.4.2.3-08",
"label" : "CP.4.2.3#08",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to extract and render medications by generic, and/or brand name."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.